Wireless routing based on data packet classifications

ABSTRACT

A method of wirelessly routing based on data packet type is disclosed. The method includes a wireless access node wirelessly receiving a data packet. The wireless access node classifies the data packet, and selects one of multiple node interfaces based on the classification of the data packet, and/or characteristics of the node interfaces. The wireless access node forwards the data packet over the selected node interface.

CROSS-REFERENCES TO RELATED APPLICATION(S)

The present application is based on and claim the benefit of U.S.Provisional Patent Application Ser. No. 60/901,162, entitled “Spectrumand Application-Based Routing”, filed on Feb. 14, 2007, the disclosureof which is hereby incorporated by reference in entirety for allpurposes.

FIELD OF THE DESCRIBED EMBODIMENT

The described embodiments relate generally to wireless communications.More particularly, the described embodiments relate to a method andapparatus for wirelessly routing based on data packet classifications.

BACKGROUND

Wireless mesh networks are gaining popularity because wirelessinfrastructures are typically easier and less expensive to deploy thanwired networks. The wireless mesh networks typically include wiredgateways that are wirelessly connected to wireless nodes, or wirelesslyconnected directly to client devices. Many wireless nodes cancollectively provide a wireless mesh, in which client devices canassociate with any of the wireless nodes.

Routing paths can be selected between the nodes of the mesh networkaccording to one or more of many possible routing selection procedures.The routing paths provide a path for data flow between a client deviceassociated with the wireless mesh network and a gateway of the meshnetwork. The gateway can be wire-connected to a wired network which isconnected, for example, to the internet. Due to the possibility ofchanging locations of the wireless nodes, and due to the typicallychanging link qualities of wireless connections, the best qualityrouting path available can vary with time. Additionally, wirelessclients typically roam from one wireless node to another wireless node.

Wireless networks can be useful for providing communications foremergency services. An advantage of wireless networks is that they canprovide network access in places and situations that wired networkscannot. For example, when the World Trade buildings were destroyed, orwhen hurricane Katrina destroyed large parts of New Orleans, much wirednetwork infrastructure was left un-useable. However, emergency accessmust not be inhibited or interfered when wireless networks are sharedbetween emergency services and general network access.

It is desirable to have wireless network that can simultaneously supportrouting of multiple types of data packets.

SUMMARY

An embodiment includes a method of wirelessly routing based on datapacket type. The method includes a wireless access node wirelesslyreceiving a data packet. The wireless access node classifies the datapacket, and selects one of multiple node interfaces based on theclassification of the data packet, and/or characteristics of the nodeinterfaces. The wireless access node forwards the data packet over theselected node interface.

Another embodiment includes a method of wirelessly routing based on datatype. The method includes a wireless access node receiving andclassifying a data packet. The wireless access node selects at least oneof a plurality of access node wireless interfaces based on theclassification of the data packet, and characteristics of the nodeinterfaces. The wireless access node forwards the data packet over theat least one selected access node wireless interface.

Another embodiment of the invention includes a method of using multipleradios of a wireless access node of a wireless network. The methodincludes selecting a 4.9 GHz radio exclusively for public safety datapackets, selecting other radios for other types of data packets, andselecting other radios for public safety data packets depending uponspecification by a network operator.

Other aspects and advantages of the described embodiments will becomeapparent from the following detailed description, taken in conjunctionwith the accompanying drawings, illustrating by way of example theprinciples of the described embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example of a wireless network that includes nodes havingmultiple types of node interfaces.

FIG. 2 shows another example of a wireless network that includes nodeshaving multiple types of uplink and downlink node interfaces.

FIG. 3 shows an example of a wireless mesh network that includeswireless access nodes having multiple types of node interfaces.

FIG. 4 shows another example of a wireless mesh network that includeswireless access nodes having multiple types of node interfaces.

FIG. 5 shows another example of a wireless mesh network that includeswireless access nodes having multiple types of node interfaces.

FIG. 6 is a flow chart that includes steps of one example of a method ofwirelessly routing based on data packet type.

FIG. 7 is a flow chart that includes steps of one example of a method ofwirelessly routing based on data packet type.

FIG. 8 is a flow chart that includes step of one example of a method ofusing multiple radios of a wireless access node of a wireless network.

DETAILED DESCRIPTION

The embodiments described include wireless access nodes that havemultiple types of interfaces. The interfaces can be selected for usedepending upon characteristics of the data packets routing through thewireless access nodes. The interfaces can include fiber, Ethernet,and/or licensed or unlicensed wireless. Client associations and routingpath selections through the wireless network can be base at least inpart on the availability of the different interfaces of the wirelessaccess nodes. At least one of the interfaces can be dedicated to, forexample, public safety information.

FIG. 1 shows an example of a wireless network that includes multiplewireless access nodes (wireless gateways) 110, 112, 114. Each of thewireless access nodes includes multiple types of node interfaces 140,141, 142. The wireless access nodes 110, 112, 114 can operate using anynumber of the node interfaces 140, 141, 142 depending on the data loadand/or the data type being routed through the wireless access nodes 110,112, 114. The node interfaces 140, 141, 142 are connected to an upstreamwired network 130, such as, the internet. The wireless access nodes 110,112, 114 provide client devices 120, 121 with access to the internet130.

Each of the node interfaces 140, 141, 142 can include a characteristicthat makes it unique with respect to the other node interfaces 140, 141,142. For example, one or more of the node interfaces 140, 141, 142 maybe more reliable, have more capacity, or be less expensive than theother node interfaces 140, 141, 142. Some of the node interfaces 140,141, 142 can operate over licensed or unlicensed wireless spectrum. Oneof more of the node interfaces 140, 141, 142 can be designated asfall-back node interfaces 140, 141, 142 to be used only when none of theother node interfaces 140, 141, 142 are available. One or more of thenode interfaces 140, 141, 142 can be dedicated for public safety.

For an embodiment, the nodes 140, 141, 142 route data base onclassifications of the data. For example, data packets that areidentified as public safety data can be given the highest priority, andtherefore, be routed through a dedicated public safety interface. Forexample, a 4.9 GHz backhaul interface can be designated as a publicsafety interface, and all public safety packets can be exclusivelyrouted through it.

Another embodiment includes each of the wireless access nodesadvertising the node interfaces of the wireless access node. Theadvertisements can be received by client devices that may or may notassociate with the wireless network. Based on the advertised wirelessaccess node uplink interfaces, the client devices can decide whether toassociate with the network, and if associating, which wireless accessnode to associate with. That is, the client devices can to at least someextent, select with wireless access node to associate with based on thenode interfaces being advertised by the wireless access node. As will bedescribed, one method of advertising the node interfaces includesappending node interface information to beacons (for example, routingbeacons) that are continually broadcast by the wireless access nodes.

FIG. 2 shows another example of a wireless network that includes nodes(wireless access point or wireless gateways) having multiple types ofnode interfaces. Here, the wireless access nodes 210, 212, 214 includemultiple upstream interfaces 230, 231, 232 and multiple downstreaminterfaces 240, 242, 244. Either or both of the upstream interfaces andthe downstream interfaces can be selected based upon data packetclassifications. That is, the wireless access nodes 210, 212, 214 canbase routing of packets through each of the interfaces base on aclassification of the data being route. The wireless access nodes 210,212, 214 provide client devices 220, 221, 222, 223 access to theinternet 130.

Each wireless access node can advertise the uplink and downlink nodeinterfaces available. The advertisement can be broadcast on one or moreof the available down link node interfaces, allowing client devices tobase selection of which wireless access node to associated with based onthe advertised node interfaces.

FIG. 3 shows an example of a wireless mesh network that includeswireless gateways having multiple types of node interfaces. The nodeinterfaces of this embodiment provide multiple uplink or backhaulinterfaces 340, 341, 342. As previously described, the gateways 310,312, 314 can advertise the backhaul interfaces available to each of thegateways 310, 312, 314. Based on the backhaul interfaces, downstreamaccess nodes 350, 352, 354, 356, 360, 362 can select routing paths to atleast one of the gateways 310, 312, 314. Client device 320, 321 canassociate with any of the access nodes or gateways.

Access Node Routing Selections

Access nodes 350, 352, 354, 356, 360, 362 are coupled either directly orindirectly to the gateways 310, 312, 314. That is, each access node iseither directly connected to one of the upstream gateways 310, 312, 314,or indirectly connected through another access node to one of theupstream gateway 310, 312, 314. Many factors node is connected to,including the backhaul interfaces of the gateways 310, 312, 314. Themesh network of FIG. 3 can include any number of additional gateways andaccess nodes. As shown in FIG. 3, clients 320, 312 can obtain access tothe network by establishing a connection to an available access node,such as, any of access nodes 360, 362.

For an exemplary embodiment, the gateways 310, 312, 314 transmit (forexample, by broadcast) routing packets (beacons), which can be used todetermine routing paths between access nodes 350, 352, 354, 356, 360,362 and the gateways 310, 312, 314 of the network. The beacons arereceived by all first-level access nodes (for example, access nodes 350,352, 354, 356), which are access nodes that are able to receive gatewaytransmitted beacons, and directly route data through to a gateway.

The beacons originated at the gateways include an identifier of thegateway and interface availability of the gateway. The beacons are usedto establish a route from each access node to a gateway. The first levelaccess nodes re-transmit (for example, by re-broadcast) the beacon data,attaching their own information to the beacon. The information indicatesto the second level access nodes that an available path to the gatewayincludes the first level access node. The rebroadcast information caninclude the addresses of all upstream access nodes along the path to thegateway access node, and the types of interfaces available at each ofthe upstream access nodes and gateways. That is, an embodiment includeseach access node that receives routing beacons, modifying the routingbeacons of a selected route by attaching an address of the access nodeand the interface types of the access node, and re-broadcasting themodified beacons.

For one embodiment, the link quality of the beacon received determineswhether that beacon is rebroadcast by the access node. If the quality ofthe beacon is above a determined threshold, it is rebroadcast.Alternatively, if the quality of the beacon is greater than the qualityof all other received beacons, the beacon is rebroadcast. Anotherembodiment includes each access node only re-broadcasting beaconsreceived from its currently-chosen default gateway (the default gatewayis the last selected upstream gateway).

Beacons can be used to determine the quality of the link in both anupstream (towards a gateway) direction, and in a downstream (away from agateway) direction. Additionally the quality of a link can be influencedby the size of the cluster the link is connected to. The upstream andthe downstream direction link qualities, and the cluster size can beused by each access node to select the best data routing path to agateway. The link qualities can be influenced by other wirelesstransmission factors such as interference, noise and fading. The linkqualities can be determined by calculating the percentage of beaconsthat are transmitted and successfully received. The link qualities canalternatively or additionally be determined by measuring a PER, BER orSNR of received routing beacons. As described, the link qualities can beinfluenced by the interfaces available at the device (gateway or accessnode) that is transmitting the beacon.

Asymmetrical characteristics of the links between access nodes and thegateways can lead to non-optimal routing selections if, for example, thequality of the upstream direction links is not included in routingdecisions by access nodes to gateways. Each gateway and access nodetransmits beacons. All access nodes and gateways that receive thebeacons can make an estimate of the quality of the link based upon thereception of the beacons. The estimates can include both upstreamdirection link quality and downstream direction link quality. Once eachaccess node has the upstream and downstream link qualities within everypossible data path to a gateway, the access node can make a selection ofthe best available data path.

Each access node has at least one upstream node, and may have aplurality of downstream nodes. Upstream nodes are the nodes that arebetween the access node and the gateway. For a level one access node,there is only one upstream node, the gateway. For a level four accessnode, there are four upstream nodes, which define the access node's pathto the gateway. Downstream nodes are nodes that receive the beacon froma particular access node, and define their path to the gateway throughthat access node.

FIG. 3 also includes a second level access nodes 360, 362. The secondlevel access nodes select that best quality links to first level accessnodes (assuming there are no links to gateways of better quality).Again, the first level access node re-transmit (rebroadcast)successfully received routing packets. The link quality can bedetermined be calculating the percentage of beacons that are transmittedand successfully received by the second level access nodes. Aspreviously described, the link quality can be additionally influenced bythe receive link quality, the availability of the interface indicatedwithin the beacons, and even the hop count of the beacons. The hop countis defined by the number of wireless hops the beacon has traveled,wherein each wireless link counts as a hop. The number of levels of theaccess nodes of the mesh network is not limited.

The various backhaul interfaces and link interfaces (uplink anddownlink) can differ in multiple ways. Similarly the different wired andwireless interfaces on an access node can differ in multiple ways. Somewireless links are more reliable than others. Some backhaul options orwireless links have higher capacity than others. Some backhaul optionsare more secure than others. Some backhaul options are more inexpensiveto use than others. Some backhaul links or wireless links might bepreferred for use based on whether they utilize licensed or unlicensedwireless links. Some backhaul options or wireless mesh options can bedesignated for use only as a fall-back. That is, they are selected whenall other options are unavailable. Some interfaces can be designated foruse to transport data only from a specific user group or application.

A network operator can additionally specify a set of rules orpreferences to guide the utilization of the different wireless frequencybands of different interfaces. For example, the operator may specifythat the 4.9 GHz band interface is exclusively for public safety use.The operator can specify that radios operating on the unlicensed 2.4 GHzband can be used to carry residential users' traffic and to carry publicsafety traffic only if a 4.9 GHz link or path is unavailable. Theoperator can specify that radios operating on an unlicensed band may beused to carry residential users' traffic and to carry public safetytraffic only if a 4.9 GHz link or path is worse in performance than anunlicensed wireless link or path. The operator can specify that publicsafety traffic has pre-emption rights over other classes of traffic overunlicensed spectrum in the event of an emergency. The operator canspecify that public safety traffic has pre-emption rights over otherclasses of traffic over unlicensed spectrum in the event that a 4.9 GHzlink is unavailable or unusable. The operator can specify that aparticular band is to be used exclusively to transport traffic that hasbeen identified as video. The operator can specify that a particularapplication has prioritized access to a particular band. Clearly, thesesuggested examples of preferences can be used on both backhaulinterfaces, and uplink and downlink interfaces of gateways and/or accessnodes of a wireless mesh network.

Embodiments of gateways incorporate intelligence about these differentcharacteristics of the different backhaul options on its backhaulinterfaces to take the above-listed differences as well asoperator-specified rules and preferences into consideration in routingtraffic over these backhaul links. Embodiments of access nodesincorporate intelligence about these different characteristics of itsdifferent wireless interfaces to take the above-listed differences aswell as operator-specified rules and preferences into consideration inrouting traffic over these wireless interfaces. The rules can beimplemented on a per-packet basis, as part of the routing decision foreach packet received by an access node or gateway.

An embodiment of a gateway includes logic to periodically test theperformance (throughput, latency and other measures), reliability andavailability of the backhaul links on each of its interfaces. Anembodiment of an access node includes logic to periodically test theperformance (throughput, latency and other measures), reliability andavailability of the wireless links on each of its wireless interfaces.

In some applications, a given backhaul interface may only be usable fora specific application or to carry data traffic from a specific usergroup. For example, there is spectrum available in the 4.9 GHz bandexclusively for public safety applications. A backhaul interface with4.9 GHz wireless backhaul can only be used to transport public safetytraffic or traffic identified as originating from or destined to publicsafety users or networks. As another example, the operator may specifythat a specific unlicensed frequency band or channel is to be usedexclusively to transport video traffic.

In one embodiment, a gateway can identify traffic as originating from ordestined to a public safety user or belonging to a public safetyapplication. In one embodiment, such identification may take place at anaccess node or gateway based on identifiers in the received data framesuch as ESSID, VLAN ID, source/destination IP address range, protocolidentifier or some other application identifier. In another embodiment,such identification can take place at an access node where the clientdevice associates and this identification may be conveyed to the gatewaythrough routing messages. For example, a user may associate andauthenticate to a public safety ESSID at an access node and getidentified as a public safety user. The access node can then convey theIP address, MAC address and other identifiers associated with the user(client device) to the gateway and identify the user as a public safetyuser. In one embodiment, an access node can identify and classifytraffic based on application characteristics and heuristics. Forexample, voice traffic has certain characteristics (small packets,regularly spaced in time) that might be used to reliably identify atraffic stream as carrying voice, even if no identifiers in a packet orframe identify the application class as voice.

When a gateway receives a data packet that has been identified as comingfrom or going to a public safety user or as belonging to a public safetyapplication, and that needs to be routed upstream, it may incorporate apreference to route the packet over the preferred (as designated by theoperator) backhaul interface.

In some situations, it is possible that a preferred backhaul interfacemight have a lower throughput than some other backhaul interface andthat it is more optimal to route the packet over an alternate backhaulinterface. For example, 4.9 GHz wireless propagation outdoors issignificantly inferior to 2.4 GHz propagation and it is possible thatthe performance of a 2.4 GHz unlicensed wireless backhaul link mightoutperform the performance of the 4.9 GHz backhaul link. In such a case,the gateway may incorporate logic to override the operator-specifiedpreference for 4.9 GHz to instead route the packet over the 2.4 GHzlink. It is also possible that the operator-preferred backhaul link isunavailable due to hardware failures or other reasons. In such a case,the gateway may override the operator-specified preference to insteadroute the packet over an alternate backhaul link.

An embodiment includes a system operator specifying that public safetyhas pre-emption rights over other traffic classes on unlicensed spectrumin the event of a failure of a 4.9 GHz backhaul link, or an emergency orother event. As another example, the operator may specify that publicsafety traffic has priority over other traffic classes on unlicensedspectrum in the event of a failure of a 4.9 GHz backhaul link, or anemergency or other event. An event such as failure of a backhaulinterface is detectable by the gateway since it can periodically performtests that evaluate the performance of the links on each of its backhaulinterfaces. These tests can include tests of last-hop links as well asend-to-end tests. When a gateway detects failure or under-performance ofa 4.9 GHz backhaul link or an operator-specified event, it can mark thelink as temporarily unusable or sub-optimal. Any public safety trafficreceived thereafter, while the 4.9 GHz link is unusable, can be routedover some other backhaul interface, such as unlicensed wirelessbackhaul. Additionally, it can be prioritized higher than other traffictransiting the backhaul interface. This can be accomplished by placingpublic safety traffic in a higher priority queue and tagging it with ahigher priority tag (such as 802.1p or IETF DSCP) that can beappropriately interpreted by upstream network equipment. Alternatively,it may temporarily stop routing all other traffic over the unlicensedwireless backhaul link, so as to maintain its availability for higherpriority public safety traffic. In another embodiment, a managementserver or network manager may detect an event such as an emergency andsend an instruction to a management server to initiate prioritizedaccess or pre-emption rights for public safety traffic over othertraffic classes using unlicensed frequency bands.

In some embodiments, it may be desired to incorporate a preference fortransporting data over certain backhaul interfaces. For example, forreasons of reliability, it may be desired to preferentially transporttraffic over a backhaul interface that consists of a wireless linkoperating over licensed spectrum. The gateway may incorporate thispreference in its routing logic. However, the routing logic may becapable of overriding this preference in the event that the preferredbackhaul interface is identified as offering poor performance or lowerperformance than some other backhaul interface that is available to beused based on the operator-specified rules.

FIG. 4 shows another example of a wireless mesh network that includeswireless gateways 410, 412, 414 having multiple types of nodeinterfaces. The node interfaces of this embodiment provide multiplebackhaul interfaces 340, 341, 342 and/or multiple downlink interfaces440, 441, 442. Both the backhaul interfaces 340, 341, 342 and themultiple downlink interfaces 440, 441, 442 can be advertised by thegateways so that downstream access nodes can select routing paths baseat least in part on the availability of the interfaces. As will bedescribed, one or more of the interfaces can be dedicated exclusively tocertain types of network data, such as, public safety.

As previously described, the access nodes 450-462 can select routingpaths to upstream gateways. However, the access nodes can includemultiple uplink interfaces. For example, access node 454 is shown havinguplink interfaces 440, 442. Therefore, based on the availability andquality of the downlink interfaces of the gateways 410, 412, 414, theaccess nodes can select multiple routing paths to multiple upstreamgateways. That is, for example, the access node 454 may select gateway412 because of its availability of an interface (such as, interface 440,which could be, for example, a 4.9 GHz band interface) that is dedicatedto public safety. However, for general data packets, a differentinterface (such as, interface 442) may provide a higher quality routingpath to the upstream gateway 414. Additionally, the interface 440 maynot be available for general data packets. That is, the interface 440may be exclusively dedicated to public safety.

An embodiment of wireless mesh access nodes includes multiple radiosoperating in multiple frequency bands. The operator-specified rules andpreferences may apply to the radios operating in the mesh.

The access nodes select routing paths based on path quality. Paths thatare selected as routing paths are those with high path quality. Anaccess node selects an upstream access node as a default route for thepurpose of forwarding traffic upstream. In one embodiment, a defaultroute is selected for each radio interface. For example a first node mayselect a second node as its 4.9 GHz default route, and a third node asits 2.4 GHz default route.

As described, access nodes may transmit routing packets or beacons toadvertise the availability of a routing path. In one embodiment, agateway can transmit routing packets advertising all of its activebackhaul interfaces and performance metrics (throughput, latency,capacity, packet loss, etc.) for each backhaul interface. These routingpackets may be transmitted on a plurality of frequency bands, dependingon the active radio interfaces on the gateway. For example, gateway Xmay advertise a 4.9 GHz backhaul interface with throughput of 10 Mbpsand latency of 20 ms and a 5 GHz backhaul interface with throughput of18 Mbps and a latency of 15 ms whereas gateway Y may advertise a 4.9 GHzbackhaul interface with throughput of 8 Mbps and latency of 40 ms and a5 GHz backhaul interface with throughput of 24 Mbps and a latency of 10ms. An access node Z receiving these routing packets may determine thatit is preferable to route public safety traffic through gateway X (sincegateway X's 4.9 GHz backhaul interface has better performance thangateway Y) and to route all other traffic through gateway Y (sincegateway Y's 5 GHz backhaul interface has better performance than gatewayX). An access node may also base its routing decisions on the quality ofthe wireless mesh links to upstream nodes. For example, access node Zmay receive routing beacons from gateway X with packet successprobability p1 over its 2.4 GHz radio, p2 over its 4.9 GHz radiointerface and p3 over its 5 GHz radio interface and receive routingbeacons from gateway Y with packet success probability q1 over its 2.4GHz radio, q2 over its 4.9 GHz radio interface and q3 over its 5 GHzradio interface. If q3>p3 and q2>p2 and p1>q1, the access node mayselect gateway Y as its 5 GHz default route and 4.9 GHz default route,but select gateway X as its 2.4 GHz default route. In one embodiment, anaccess node can transmit routing beacons advertising its active routingpaths over a plurality of frequency bands. Downstream access nodereceiving these beacons can make routing decisions to route through thisaccess node or through alternatives. Different routes may exist fordifferent classes of traffic, different applications and acrossdifferent frequency bands. The routing decisions may further incorporateperformance criteria for the different paths as well asoperator-specified rules and preferences.

The access nodes can identify and classify data traffic as describedpreviously. Access nodes can also measure the performance of theirpaths. Based on the classification and on measured performance data foreach of the paths in use, an access node that receives a data packet canapply operator-specified rules and preferences to guide its routingdecision per-packet. This decision can also incorporate measuredperformance characteristics of each path. For instance, if an accessnode's 4.9 GHz path is measured as having low throughput, the accessnode can decide to route data packets classified as public safetytraffic over another interface that has a better throughput, until the4.9 GHz path improves in performance. The access nodes can implementrouting rules such as exclusive or prioritized or pre-emptible use ofparticular bands for specific applications or user groups and canimplement fallback policies in case of certain events or degradations.

In one embodiment, an access node can incorporate a preference for usingan unlicensed frequency band to transport data traffic over using alicensed band. Since licensed spectrum is scarce, it may be desirable toreserve the use of that spectrum for communication with clients, whileminimizing its use within the mesh. In one embodiment, the access nodemay switch to using a licensed band to transport data within the mesh ifits unlicensed routing paths degrade in quality or performance.

FIG. 5 shows another example of a wireless mesh network that includeswireless access nodes (gateways and access nodes) having multiple typesof node interfaces. For this embodiment, the gateways 410, 412, 414include multiple backhaul node interfaces 340, 341, 342, multipledownlink interfaces 440, 441, 442, and the access nodes 550, 552, 554,556 include multiple uplink node interfaces 440, 441, 442 and multipledownlink node interfaces 540, 541, 542. As previously described, thegateways can include information of the available interfaces inbroadcast routing beacons. The access node can attached availableinterfaces in re-broadcast routing beacons.

Multiple Routine Selections

The access nodes 550-565 of the example of a wireless mesh network ofFIG. 5 can select routing path using method similar to those previouslydescribed. However, the gateways, and the first-order and second-orderaccess node can all have multiple uplink interfaces and multipledownlink interfaces. As previously described, the availability ofinterfaces can be included within the routing beacons. The availabilityof multiple interfaces on the uplinks and downlinks enable multiplerouting paths to multiple gateways to be selected by the access nodes.That is, any access node can select multiple routing paths to one ormore upstream gateways.

As shown in FIG. 5, for example, the second-order access node 561 hasmultiple possible routing paths to the gateways 410, 412. Potentiallytwo routing path can be selected to a single gateway 410, andadditionally or alternatively, a routing path can be selected to thegateway 412. The downstream access nodes can receive routing beaconsover multiple interfaces, and therefore, can select different routingpaths through different combinations of downlink and uplink interfaces.

FIG. 6 is a flow chart that includes steps of one example of a method ofwirelessly routing based on data packet type. A first step 610 includesa wireless access node wirelessly receiving a data packet. A second step620 includes the wireless access node classifying the data packet. Athird step 630 includes the wireless access node selecting at least oneof a plurality of node interfaces based on at least one of theclassification of the data packet, and characteristics of the nodeinterfaces. A fourth step 640 includes the wireless access nodeforwarding the data packet over the at least one selected nodeinterface.

Generally, selecting at least one of a plurality of node interfacesbased on the classification of the data packet includes determiningperformance characteristics of the node interfaces, and matching theperformance characteristics of the node interfaces with theclassification of the data packet. A non-exhaustive list of exemplaryperformance characteristics includes information of whether theinterface is alive, a security of the interface, a latency associatedwith the interface, a capacity of the interface, throughput of theinterface, reliability of the interface, cost of the interface, afrequency band of the interface, whether the interface includes alicensed frequency band or an unlicensed frequency band, traffic load ofthe interface, air-time noise of the interface. Additionally, selectingthe access node interfaces based on the classification of the datapacket can include receiving preferences specified by a networkoperator, and matching the node interfaces with the classification ofthe data packet based on the specified preferences.

For an embodiment, the wireless access node periodically testsperformance characteristics of the node interfaces. More specifically, agateway or access node can include logic to periodically testperformance (throughput, latency and other measures) reliability andavailability of the backhauls and wireless links on each of itsinterfaces.

Data classification of the data packets enables the wireless access nodeto optimally select the best node interfaces for different types of datapackets. For example, public safety data packets can be routed through anode interface (such as, a 4.9 GHz wireless link) that is dedicated topublic safety information.

As previously described, an embodiment of the wireless mesh networkincludes gateways that originate routing beacons. The routing beaconscan include interface characteristics information in routing beaconsoriginating at the gateways, allowing downstream devices to factor theavailable node interfaces into routing selection decisions. Aspreviously described, the node interfaces can include either or bothupstream links and down stream links of gateways and access node of thewireless mesh network.

Access nodes of the wireless mesh network can select one or more routingpaths to one or more gateways based at least in part on backhaulinterfaces advertised by upstream gateways. Once a routing path has beenselected, one embodiment includes the access nodes rebroadcasts routingbeacons successfully received through a selected routing path, whereinthe rebroadcast beacons additionally include information ofcharacteristics of node interfaces of the access node. Downstream accessnodes can base selection of routing paths through upstream access nodebased at least in part on the availability of the node interfaces of theupstream access nodes.

A non-exhaustive list of examples of node interfaces includes 2.4 GHzinterface, a 5 GHz interface, a WiMAX interface, 3G interface, a 4Ginterface. A non-exhaustive list of examples of data packetclassification includes public safety, a user group, voice traffic,video traffic, 802.16 user data, 802.11 user data, public safety videotraffic, public safety voice traffic.

For one embodiment, at least one of the node interfaces is designated asa fall-back interface to be selected only when all other node interfacesare not available. For example, a 2.4 GHz node interface can be selectedfor public safety data packets only if a 4.9 GHz node interface is notavailable. Another embodiment includes selecting the 2.4 GHz nodeinterface for public safety data packets only if the 4.9 GHz nodeinterface provides lower quality performance than the 2.4 GHz nodeinterface. Another embodiment includes a preference for selecting anunlicensed frequency node interface over a licensed frequency nodeinterface.

The node interface selection can include a preemptive selection. Thatis, events (that is, the occurrence of an event) can trigger, forexample, public safety data packets to preempt other types of datapackets for all available node interfaces. The trigger can be caused byan event, or by a network manager. The preemption can cause publicsafety data packets to preempt other types of data packets for allavailable node interfaces if the 4.9 GHz node interface is unavailable.

For an embodiment, the data packets are identified by identifiers withinreceived data frames. For example, a gateway can identify traffic asoriginating. Examples of possible identifiers includes an src IPaddress, a destination IP address, an SSID, a VLAN ID, an 802.11e QoStags, DSCP tags, TCP or UDP port numbers. For one embodiment, the datapackets are identified by a node a client is connects to, and the nodepropagates the identification through routing packets. The node canidentify and classify data packets of the client base on applicationheuristics and characteristics. That is, for example, the node canidentify the data as voice or video data by monitoring thecharacteristics data. That is, the continuous, periodic nature andbandwidth of the data can be used to identify the data as voice orvideo.

FIG. 7 is a flow chart that includes steps of one example of a method ofwirelessly routing based on data packet type. A first step 710 includesa wireless access node receiving a data packet. A second step 720includes the wireless access node classifying the data packet. A thirdstep 730 includes the wireless access node selecting at least one of aplurality of access node wireless interfaces based on the classificationof the data packet, and characteristics of the node interfaces. A fourthstep 740 includes the wireless access node forwarding the data packetover the at least one selected access node wireless interface.

As previously mentioned, an embodiment includes the wireless accessnodes selecting an upstream routing path to a gateway based on backhaulinterfaces characteristics of the gateway. Also as mentioned, thewireless access node can receive the information of the backhaulinterfaces of the gateway from routing beacon originating at thegateway. The access node re-broadcast routing beacons originating at thegateway after attaching information of interface characteristics of theaccess node.

FIG. 8 is a flow chart that includes step of one example of a method ofusing multiple radios of a wireless access node of a wireless network. Afirst step 810 includes selecting a 4.9 GHz radio exclusively for publicsafety data packets. A second step 820 includes selecting other radiosfor other types of data packets. A third step 830 includes selectingother radios for public safety data packets depending upon specificationby a network operator.

For an embodiment, if the 4.9 GHz radio interface is not available, thennetwork operator can specify that the public safety data packets are touse an unlicensed band radio. For another embodiment, if the 4.9 GHzradio provides lower quality performance than an unlicensed band radio,then the network operator can specify that the public safety datapackets are to use an unlicensed band radio of the 4.9 GHz radio providelower quality performance than an unlicensed band radio.

Another embodiment includes providing public safety data packets withpreemptive rights to all radios of the wireless access node if triggeredby detection an emergency event. That is, if an emergency event istriggered, the communication (for example, public safety information)preempts all other traffic, and is given priority over all other typesof data packets. Another embodiment includes providing public safetydata packets with preemptive rights to all radios of the wireless accessnode if the 4.9 GHz radio is unavailable.

Although specific embodiments have been described and illustrated, theembodiments are not to be limited to the specific forms or arrangementsof parts so described and illustrated.

1. A method of wirelessly routing based on data packet type, comprising:a wireless access node wirelessly receiving a data packet; the wirelessaccess node classifying the data packet; the wireless access nodeselecting at least one of a plurality of node interfaces based on atleast one of the classification of the data packet, and performancecharacteristics of the node interfaces; and the wireless access nodeforwarding the data packet over the at least one selected nodeinterface; wherein the wireless access node periodically testsperformance characteristics of the node interfaces.
 2. The method ofclaim 1, wherein selecting at least one of a plurality of nodeinterfaces based on the classification of the data packet comprises:determining performance characteristics of the node interfaces; andmatching the performance characteristics of the node interfaces with theclassification of the data packet.
 3. The method of claim 2, wherein theperformance characteristics comprise at least one of whether theinterface is alive, a security of the interface, latency associated withthe interface, a capacity of the interface, throughput of the interface,reliability of the interface, cost of the interface, a frequency band ofthe interface, whether the interface includes a licensed frequency bandor an unlicensed frequency band, traffic load of the interface, air-timenoise of the interface.
 4. The method of claim 1, wherein selecting atleast one of a plurality of access node interfaces based on theclassification of the data packet comprises: receiving preferencesspecified by a network operator; and matching the node interfaces withthe classification of the data packet based on the specifiedpreferences.
 5. The method of claim 1, wherein the plurality of nodeinterfaces comprises at least one of a 2.4 GHz interface, a 4.9 GHzinterface, a WiMAX interface, 3G interface, a 4G interface.
 6. Themethod of claim 1, wherein the data packet classification comprisesclassifying packets as at least one of public safety, a user group,voice traffic, video traffic, 802.16 user data, 802.11 user data, publicsafety video traffic, public safety voice traffic.
 7. The method ofclaim 1, wherein a 2.4 GHz node interface is selected for public safetydata packets only if a 4.9 GHz node interface does not meet certainpre-defined performance thresholds.
 8. The method of claim 1, wherein a2.4 GHz node interface is selected for public safety data packets onlyif a 4.9 GHz node interface provides lower quality performance than the2.4 GHz node interface.
 9. The method of claim 1, wherein the wirelessaccess node incorporates a preference for selecting an unlicensedfrequency node interface over a licensed frequency node interface. 10.The method of claim 1, wherein the wireless access node incorporates apreference for selecting a licensed frequency node interface over anunlicensed frequency node interface.
 11. The method of claim 1, whereinoccurrence of an event causes public safety data packets to preemptother types of data packets for all available node interfaces if the 4.9GHz node interface is unavailable.
 12. The method of claim 1, furthercomprising the data packets being identified by identifiers withinreceived data frames.
 13. The method of claim 1, wherein identifierscomprise at least one of an src IP address, a destination IP address, anSSID, a VLAN ID, an 802.11e QoS tags, DSCP tags, TCP or UDP portnumbers.
 14. A method of wirelessly routing based on data packet type,comprising: a wireless access node wirelessly receiving a data packet;the wireless access node classifying the data packet; the wirelessaccess node selecting at least one of a plurality of node interfacesbased on at least one of the classification of the data packet, andperformance characteristics of the node interfaces; and the wirelessaccess node forwarding the data packet over the at least one selectednode interface; wherein the wireless access node is a gateway of awireless mesh network.
 15. The method of claim 14, wherein theinterfaces are backhaul interfaces of the gateway.
 16. The method ofclaim 14, wherein the interfaces are downstream links of the gateway.17. The method of claim 14, wherein the gateway includes interfacecharacteristics information in routing beacons originating at thegateway.
 18. A method of wirelessly routing based on data packet type,comprising: a wireless access node wirelessly receiving a data packet;the wireless access node classifying the data packet; the wirelessaccess node selecting at least one of a plurality of node interfacesbased on at least one of the classification of the data packet, andperformance characteristics of the node interfaces; and the wirelessaccess node forwarding the data packet over the at least one selectednode interface; wherein the wireless access node is an access node of awireless mesh network, and the interfaces are a part of at least one ofupstream links and down stream links of the access node.
 19. The methodof claim 18, wherein the access node selects a routing path to a gatewaybased at least in part on backhaul interfaces of upstream gateways. 20.The method of claim 19, wherein access nodes additionally select pathsbased on node interfaces available at upstream access nodes.
 21. Themethod of claim 18, wherein the access node rebroadcasts routing beaconssuccessfully received through a selected routing path, the rebroadcastbeacons additionally including information of characteristics of nodeinterfaces of the access node.
 22. A method of wirelessly routing basedon data packet type, comprising: a wireless access node wirelesslyreceiving a data packet; the wireless access node classifying the datapacket; the wireless access node selecting at least one of a pluralityof node interfaces based on at least one of the classification of thedata packet, and performance characteristics of the node interfaces; andthe wireless access node forwarding the data packet over the at leastone selected node interface; wherein at least one of the node interfacesis designated as a fall-back interface to be selected only when someother node interfaces do not meet certain pre-defined performancethresholds.
 23. A method of wirelessly routing based on data packettype, comprising: a wireless access node wirelessly receiving a datapacket; the wireless access node classifying the data packet; thewireless access node selecting at least one of a plurality of nodeinterfaces based on at least one of the classification of the datapacket, and performance characteristics of the node interfaces; and thewireless access node forwarding the data packet over the at least oneselected node interface; wherein occurrence of an event causes publicsafety data packets to preempt other types of data packets for allavailable node interfaces.
 24. The method of claim 23, wherein theoccurrence of the event is signaled by a network manager.
 25. A methodof wirelessly routing based on data packet type, comprising: a wirelessaccess node wirelessly receiving a data packet; the wireless access nodeclassifying the data packet; the wireless access node selecting at leastone of a plurality of node interfaces based on at least one of theclassification of the data packet, and performance characteristics ofthe node interfaces; and the wireless access node forwarding the datapacket over the at least one selected node interface; the data packetsbeing identified by a node a client is connects to, and the nodepropagating the identification through routing packets; wherein the nodeidentifies and classifies data packets of the client base on applicationheuristics and characteristics.
 26. A method of wirelessly routing basedon data type, comprising: a wireless access node receiving a datapacket; the wireless access node classifying the data packet; thewireless access node selecting at least one of a plurality of accessnode wireless interfaces based on the classification of the data packet,and characteristics of the node interfaces; the wireless access nodeforwarding the data packet over the at least one selected access nodewireless interface; the wireless access node selecting an upstreamrouting path to a gateway based on backhaul interfaces characteristicsof the gateway.
 27. The method of claim 26, wherein the wireless accessnode receives information of the backhaul interfaces of the gateway fromrouting beacon originating at the gateway.
 28. The method of claim 27,further comprising the access node re-broadcasting routing beaconsoriginating at the gateway after attaching information of interfacecharacteristics of the access node.